Received: from onelist.com (pop.onelist.com [209.207.135.253])
by osf1.gmu.edu (8.8.8/8.8.8) with SMTP id PAA23213
for <mcox4@osf1.gmu.edu>; Sun, 1 Aug 1999 15:29:18 -0400 (EDT)
Received: (qmail 24285 invoked by alias); 1 Aug 1999 19:28:50 -0000
Received: (qmail 24276 invoked from network); 1 Aug 1999 19:28:49 -0000
Received: from unknown (HELO mail.enterprise.net) (194.72.192.18) by pop.onelist.com with SMTP; 1 Aug 1999 19:28:49 -0000
Received: from enterprise.net (andrewcrowe@max03-077.enterprise.net [194.72.196.77]) by mail.enterprise.net (8.8.5/8.8.5) with SMTP id UAA19234 for <amos-list@onelist.com>; Sun, 1 Aug 1999 20:29:13 +0100 (GMT/BST)
Subject: [amos-list] Re: 2nd mouse & Floating point
Status: O
X-Status:
From: Andrew Crowe <andrewcrowe@enterprise.net>
Hi Everybody,
> Also, I found on Aminet a doc on optimising AMOS
> code. One
> suggestion was that floating point calculations,
> which is supposed
> involved with arrays like: PLAYER#() are _very_
> slow. I've been
> using these arrays heaps in my new tank code! I can
> not afford
> for the game to be slow. What do other people know
> about this?
Ah, floating point no's are around 3 to 4 times slower then integer when compiled, but so what? My James Bond game uses a lot of floating point stuff and that runs fine, if it didn't have to contend with the blitter's speed it'd run at 50fps ;).
If you want the game to remain at the same speed, add an automatic frame skipper, and store stuff like sin/cos's in a table instead of calling them directly.
See ya.
--
Manta Soft - Amiga programing & web page designing